Publish ioxide.Kestrel: add missing pack step + README badge#85
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #84. That PR was squash-merged at the version-bump commit, before the publish-wiring commit landed — so
maingot theioxide.Kestrelproject but not the workflow step that packs/publishes it (nor the README badge). As a result the post-merge run packed the other five packages but notioxide.Kestrel, so it never reached nuget.org.This adds:
Pack ioxide.Kestrelstep in.github/workflows/build.yml(theartifacts/*.nupkgpush then includes it).ioxide.Kestrelnuget badge in the README.On merge to
main, the Build and Publish workflow will pack and pushioxide.Kestrel0.0.13 to nuget.org + GitHub Packages (the already-published 0.0.13 packages no-op via--skip-duplicate).